We have several folders in our DOORS structure that in most cases should be folders, but periodically we want to archive the modules in the folders. Our plans are to switch the folders to projects, run the archive, and then switch them back to folders. From an execution standpoint, switching back and forth between folders and projects is straightforward and easy, but I was wondering if there are any underlying negative side effects of switching between projects and folders that I am unaware of that would indicate our plan of periodically switching is not a good idea?
|
Re: Are there any hidden side effects of switching between project and folder Paul Miller |
Re: Are there any hidden side effects of switching between project and folder SystemAdmin - Wed Nov 03 17:33:36 EDT 2010 Paul Miller |
Re: Are there any hidden side effects of switching between project and folder The real trick is to make sure you switch it BACK to a folder when you are done. Also, the folks getting the archive need to know that they restore the 'project' and should switch it to a folder as well. The OCD Twit in me is encouraged to rename the target folder with suffix "_ConvertBackToFolder", e.g. rename "MyReqs" to "MyReqs_ConvertBackToFolder", then convert to Project, then archive, then convert back, then rename removing the suffix. that stops someone else from slipping in there and resolves the coordination issue, such as if DOORS crashes.
|